Libraries tagged by EVE API

A simple to use API library for Eve-Central.

Go to Download

Adds support for adding SparkPost options via the X-MSYS-API header, even when using the API implementation

Go to Download

A PHP Library to access EVE Online's CREST API

Go to Download

Liten is a small, simple, and restful micro framework. Even though it is small, you can still use it to build intelligent and dynamic restful api's.

Go to Download

a all in 1 package to acces the full api of eve online in php

Go to Download

Provides automatic EVE Online Api fetching to your Symfony2 project.

Go to Download

API Negotiation Layer for The Eve API.

Go to Download

Collections of abstract laravel jobs to interact with eves online ESI endpoints

Go to Download

SeAT EVE API Integration

Go to Download

EVE API Client, used by Tz7 projects

Go to Download

Symfony2 EVE API Bundle, used by Tz7 projects

Go to Download

A package for interacting with and storing data from the EVE Online ESI API, along with Laravel Eloquent models for the retrieved data.

Go to Download

A pretty library to help developers build RESTful APIs lightly, quickly and properly even without writing code

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.44) is used. For example, calling `/info` is the same as calling `/v1.44/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

Auto-generated EVE ESI swagger client library

Go to Download